Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Previous Next
Subject: Multiple Traveler Servers in unique configuration
Feedback Type: Question
Product Area: Notes Traveler
Technical Area: Administration
Platform: Windows
Release: 8.5.3
Reproducible: Not applicable

We have somewhat of a unique setup we are trying to implement within our environment. Granted, we are running Domino 9.0 with Traveler 9.0 installed, but I was hoping to find someone here who might have some input than to post only in the 9 forum, or cross-post in both at the same time.

We currently have Traveler online and serving iPhones. We recently installed a BES10 server which is having some difficulty connecting to the Traveler server, due to network security issues. Essentially, requests made from our internal network are disallowed to travel out, then back in, to connect to the DMZ.

I was asked to setup another server on the internal network, and basically run a Traveler server for iPhone users (sitting in the DMZ), but also have an internal Traveler Server that could handle the request from the BES10 server. This way, requests from BES10 would not have to be routed out of the network, back into our DMZ.

I have the server setup internally, but want to use the same Lotus Traveler database. Since we already have Z10 devices in the lotustraveler.nsf, the only configuration I believe I would require changing, would be on the BES10 server, setting the user's Traveler profile to point to the Traveler server on the internal network.

Since we allow Traveler in the DMZ (primary) to communicate over port 1352 to the Traveler server internally located on the network (secondary), I am able to maintain Domino Directory replication.

I just did not know if my thought process was reasonable or achieveable. As I see it, if I had the same lotustraveler.nsf database on both servers, I could switch a Z10 user from talking to the primary server in the DMZ to the secondary server in the DMZ, since their device would already be registered in lotustraveler.nsf.

I have not attempted to shut both servers down, copy lotustraveler.nsf, at the file level, to the secondary server, and was hoping someone else might be able to share if they've done this, or if there are any hang-ups I might encounter if I attempt to do this.

Brian


Feedback number WEBB99MPQK created by ~Julia Quetjipytexings on 07/15/2013

Status: Open
Comments:





Printer-friendly

Search this forum

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS